|
2020-01-29 09:09 developer |
Abnormal_Multiview.jpg (2,115 bytes) |
|
2020-01-29 09:18 developer |
Abnormal_Multiview-2.jpg (199,070 bytes) |
|
|
Hi Jason, 1. It looks like this issue happens only while STB is set as 1080i HDMI output. Could you help to confirm it ? 2. What does 'Abnormal_Multiview.jpg' mean ? Is it 'Black screen' ? 3. It is hard to simulate Multiview environment here. Please help to get log while issue happens. Thanks ! |
|
|
hi kerwin PSB 1. It looks like this issue happens only while STB is set as 1080i HDMI output. Could you help to confirm it ? -->[Jason] yes . it happen on 1080i resolution. 2. What does 'Abnormal_Multiview.jpg' mean ? Is it 'Black screen' ? --> [Jason] first time i added a wrong picture., please remove it, I don't have an authority to remove it. 3. It is hard to simulate Multiview environment here. Please help to get log while issue happens. --> please see an attached log. is this issue related below log? ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 01-30 14:01:57.167 3103 3272 E MesonHwc: setup, layer->mZorder=0, mFramebuffers.size=3,mFbType=6, mCompositionType=0 01-30 14:01:57.167 3103 3272 E MesonHwc: pickoutOsdFbs, mZorder=0, mFramebuffers.size=3,mFbType=6, mCompositionType=7, bRemove=1 01-30 14:01:57.167 3103 3272 E MesonHwc: pickoutOsdFbs, mZorder=1, mFramebuffers.size=2,mFbType=7, mCompositionType=7, bRemove=1 01-30 14:01:57.167 3103 3272 E MesonHwc: pickoutOsdFbs, mZorder=2, mFramebuffers.size=1,mFbType=2, mCompositionType=2, bRemove=0 |
|
|
hi kerwin is there update ? please give a result of review for an attached log. |
|
|
Hi Jason, I see an unusual message in the log but I am not sure if it is the root cause. This message only appears after STB is set to 1080i60 output. I need to pass log to AML for analysis. However, we don't have confidence to fix this issue soon because of "Wuhan pneumonia". AML RDs are not back to work yet. -------------------------------------------------------------------------------------------------------------------------------------- 01-30 14:01:54.481 3103 3272 E MesonHwc: Unknown compostition type(-1426921460) 01-30 14:01:54.481 3103 3272 E MesonHwc: pickoutOsdFbs, mZorder=1, mFramebuffers.size=3,mFbType=12, mCompositionType=-1426921460, bRemove=1 01-30 14:01:54.481 3103 3272 E MesonHwc: pickoutOsdFbs, mZorder=2, mFramebuffers.size=2,mFbType=2, mCompositionType=2, bRemove=0 01-30 14:01:54.483 3103 3272 I MesonHwc: not support video fb type: 12 |
|
|
Hi Jason, In order to check issue is in video or OSD layer, please help to do tests and check if abnormal output exists or not 1. reproduce abnormal output in Multiview then follow commands below to disable video layer cat /sys/class/video/disable_video echo 1 > /sys/class/video/disable_video echo 1 > /sys/class/video/disable_videopip cat /sys/class/video/axis_pip ==> make a screen capture or take a picture by mobile phone, then reboot Eagle box 2. reproduce abnormal output in Multiview then follow commands below to disable OSD layer echo 1 > /sys/class/graphics/fb0/osd_display_debug echo 1 > /sys/class/graphics/fb0/blank echo 1 > /sys/class/graphics/fb1/osd_display_debug echo 1 > /sys/class/graphics/fb1/blank ==> make a screen capture or take a picture by mobile phone Thanks ! |
|
|
hi kerwin please see a screen shot. although input value as your guide, it still show abnormal on multivew. as talk in webchat, please give a new fw with new AML' patch. Thanks Value#1.JPG (33,954 bytes) Value#2.JPG (30,671 bytes) abnormal_multivew2.jpg (171,316 bytes) |
|
|
Hi Jason, Please use below test FW to verification BFX-AT100_513: https://drive.google.com/drive/folders/1h8cYY4hpUQswvFX-n8RyMrbSeVRCgEJ9?usp=sharing BFX-UH200_513: https://drive.google.com/drive/folders/1pJxX7Bvw3X8x3PFaF0kCf0ngNkT5qmat?usp=sharing |
|
|
hi Dixon your test fw is ok for this issue. I heard from AML about technical note of this patch. but i don't understand it. please explain it more easily. why is related to aligned 32byte of write buffer about showing white noise? -------------------------------------------------------------------------------------------------------- The issue is caused by wrong canvas stride setting of vpp mif. The streaming size is 1920x3264 h265, when issue happened, it should be 1/16 double write buffer. So 1920/16 = 480, it is 32 bytes aligned, not 64 bytes aligned. ----------------------------------------------------------------------------------------------------- this mantis will be changed as resolved. Thanks |
- yk.jung ( (ALTech) Younkwang Jung ) developer
